Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update driver adapters directory (minor) #4843

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 27, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@cloudflare/workers-types 4.20240405.0 -> 4.20240614.0 age adoption passing confidence
@effect/schema (source) 0.64.20 -> 0.67.23 age adoption passing confidence
@types/node (source) 20.12.7 -> 20.14.2 age adoption passing confidence
esbuild 0.20.2 -> 0.21.5 age adoption passing confidence
ts-pattern 5.1.1 -> 5.2.0 age adoption passing confidence
tsup (source) 8.0.2 -> 8.1.0 age adoption passing confidence
tsx (source) 4.7.2 -> 4.15.5 age adoption passing confidence
undici (source) 6.13.0 -> 6.19.0 age adoption passing confidence
wrangler (source) 3.50.0 -> 3.60.3 age adoption passing confidence

Release Notes

cloudflare/workerd (@​cloudflare/workers-types)

v4.20240614.0

Compare Source

v4.20240605.0

Compare Source

v4.20240603.0

Compare Source

v4.20240529.0

Compare Source

v4.20240524.0

Compare Source

v4.20240512.0

Compare Source

v4.20240502.0

Compare Source

v4.20240423.0

Compare Source

v4.20240419.0

Compare Source

Effect-TS/effect (@​effect/schema)

v0.67.23

Compare Source

Patch Changes

v0.67.22

Compare Source

Patch Changes

v0.67.21

Compare Source

Patch Changes

v0.67.20

Compare Source

Patch Changes
  • #​2926 4c6bc7f Thanks @​gcanti! - Add propertyOrder option to ParseOptions to control the order of keys in the output, closes #​2925.

    The propertyOrder option provides control over the order of object fields in the output. This feature is particularly useful when the sequence of keys is important for the consuming processes or when maintaining the input order enhances readability and usability.

    By default, the propertyOrder option is set to "none". This means that the internal system decides the order of keys to optimize parsing speed. The order of keys in this mode should not be considered stable, and it's recommended not to rely on key ordering as it may change in future updates without notice.

    Setting propertyOrder to "input" ensures that the keys are ordered as they appear in the input during the decoding/encoding process.

    Example (Synchronous Decoding)

    import { Schema } from "@​effect/schema";
    
    const schema = Schema.Struct({
      a: Schema.Number,
      b: Schema.Literal("b"),
      c: Schema.Number,
    });
    
    // Decoding an object synchronously without specifying the property order
    console.log(Schema.decodeUnknownSync(schema)({ b: "b", c: 2, a: 1 }));
    // Output decided internally: { b: 'b', a: 1, c: 2 }
    
    // Decoding an object synchronously while preserving the order of properties as in the input
    console.log(
      Schema.decodeUnknownSync(schema)(
        { b: "b", c: 2, a: 1 },
        { propertyOrder: "original" },
      ),
    );
    // Output preserving input order: { b: 'b', c: 2, a: 1 }

    Example (Asynchronous Decoding)

    import { ParseResult, Schema } from "@​effect/schema";
    import type { Duration } from "effect";
    import { Effect } from "effect";
    
    // Function to simulate an asynchronous process within the schema
    const effectify = (duration: Duration.DurationInput) =>
      Schema.Number.pipe(
        Schema.transformOrFail(Schema.Number, {
          decode: (x) =>
            Effect.sleep(duration).pipe(Effect.andThen(ParseResult.succeed(x))),
          encode: ParseResult.succeed,
        }),
      );
    
    // Define a structure with asynchronous behavior in each field
    const schema = Schema.Struct({
      a: effectify("200 millis"),
      b: effectify("300 millis"),
      c: effectify("100 millis"),
    }).annotations({ concurrency: 3 });
    
    // Decoding data asynchronously without preserving order
    Schema.decode(schema)({ a: 1, b: 2, c: 3 })
      .pipe(Effect.runPromise)
      .then(console.log);
    // Output decided internally: { c: 3, a: 1, b: 2 }
    
    // Decoding data asynchronously while preserving the original input order
    Schema.decode(schema)({ a: 1, b: 2, c: 3 }, { propertyOrder: "original" })
      .pipe(Effect.runPromise)
      .then(console.log);
    // Output preserving input order: { a: 1, b: 2, c: 3 }

v0.67.19

Compare Source

Patch Changes
  • #​2916 cd7496b Thanks @​gcanti! - Add support for AST.Literal in Schema.TemplateLiteral, closes #​2913

  • #​2915 349a036 Thanks @​gcanti! - Align constructors arguments:

    • Refactor Class interface to accept options for disabling validation
    • Refactor TypeLiteral interface to accept options for disabling validation
    • Refactor refine interface to accept options for disabling validation
    • Refactor BrandSchema interface to accept options for disabling validation

    Example

    import { Schema } from "@​effect/schema";
    
    const BrandedNumberSchema = Schema.Number.pipe(
      Schema.between(1, 10),
      Schema.brand("MyNumber"),
    );
    
    BrandedNumberSchema.make(20, { disableValidation: true }); // Bypasses validation and creates the instance without errors
  • Updated dependencies [8c5d280, 6ba6d26, 3f28bf2, 5817820]:

    • effect@3.2.9

v0.67.18

Compare Source

Patch Changes

v0.67.17

Compare Source

Patch Changes
  • #​2892 d9d22e7 Thanks @​gcanti! - Schema

    • add propertySignature API interface (with a from property)
    • extend optional API interface with a from property
    • extend optionalWithOptions API interface with a from property
  • #​2901 3c080f7 Thanks @​gcanti! - make the AST.TemplateLiteral constructor public

  • #​2901 3c080f7 Thanks @​gcanti! - add support for string literals to Schema.TemplateLiteral and TemplateLiteral API interface.

    Before

    import { Schema } from "@​effect/schema";
    
    // `https://${string}.com` | `https://${string}.net`
    const MyUrl = Schema.TemplateLiteral(
      Schema.Literal("https://"),
      Schema.String,
      Schema.Literal("."),
      Schema.Literal("com", "net"),
    );

    Now

    import { Schema } from "@​effect/schema";
    
    // `https://${string}.com` | `https://${string}.net`
    const MyUrl = Schema.TemplateLiteral(
      "https://",
      Schema.String,
      ".",
      Schema.Literal("com", "net"),
    );
  • #​2905 7d6d875 Thanks @​gcanti! - add support for unions to rename, closes #​2904

  • #​2897 70cda70 Thanks @​gcanti! - Add encodedBoundSchema API.

    The encodedBoundSchema function is similar to encodedSchema but preserves the refinements up to the first transformation point in the
    original schema.

    Function Signature:

    export const encodedBoundSchema = <A, I, R>(schema: Schema<A, I, R>): Schema<I>

    The term "bound" in this context refers to the boundary up to which refinements are preserved when extracting the encoded form of a schema. It essentially marks the limit to which initial validations and structure are maintained before any transformations are applied.

    Example Usage:

    import { Schema } from "@&#8203;effect/schema";
    
    const schema = Schema.Struct({
      foo: Schema.String.pipe(Schema.minLength(3), Schema.compose(Schema.Trim)),
    });
    
    // The resultingEncodedBoundSchema preserves the minLength(3) refinement,
    // ensuring the string length condition is enforced but omits the Trim transformation.
    const resultingEncodedBoundSchema = Schema.encodedBoundSchema(schema);
    
    // resultingEncodedBoundSchema is the same as:
    Schema.Struct({
      foo: Schema.String.pipe(Schema.minLength(3)),
    });

    In the provided example:

    • Initial Schema: The schema for foo includes a refinement to ensure strings have a minimum length of three characters and a transformation to trim the string.
    • Resulting Schema: resultingEncodedBoundSchema maintains the minLength(3) condition, ensuring that this validation persists. However, it excludes the trimming transformation, focusing solely on the length requirement without altering the string's formatting.
  • Updated dependencies [fb91f17]:

    • effect@3.2.8

v0.67.16

Compare Source

Patch Changes
  • #​2890 5745886 Thanks @​gcanti! - Fix constructor type inference for classes with all optional fields, closes #​2888

    This fix addresses an issue where TypeScript incorrectly inferred the constructor parameter type as an empty object {} when all class fields were optional. Now, the constructor properly recognizes arguments as objects with optional fields (e.g., { abc?: number, xyz?: number }).

  • Updated dependencies [6801fca]:

    • effect@3.2.7

v0.67.15

Compare Source

Patch Changes

v0.67.14

Patch Changes
  • #​2851 c5846e9 Thanks @​gcanti! - Add tag and TaggedStruct constructors.

    In TypeScript tags help to enhance type discrimination and pattern matching by providing a simple yet powerful way to define and recognize different data types.

    What is a Tag?

    A tag is a literal value added to data structures, commonly used in structs, to distinguish between various object types or variants within tagged unions. This literal acts as a discriminator, making it easier to handle and process different types of data correctly and efficiently.

    Using the tag Constructor

    The tag constructor is specifically designed to create a property signature that holds a specific literal value, serving as the discriminator for object types. Here's how you can define a schema with a tag:

    import { Schema } from "@&#8203;effect/schema";
    
    const User = Schema.Struct({
      _tag: Schema.tag("User"),
      name: Schema.String,
      age: Schema.Number,
    });
    
    assert.deepStrictEqual(User.make({ name: "John", age: 44 }), {
      _tag: "User",
      name: "John",
      age: 44,
    });

    In the example above, Schema.tag("User") attaches a _tag property to the User struct schema, effectively labeling objects of this struct type as "User". This label is automatically applied when using the make method to create new instances, simplifying object creation and ensuring consistent tagging.

    Simplifying Tagged Structs with TaggedStruct

    The TaggedStruct constructor streamlines the process of creating tagged structs by directly integrating the tag into the struct definition. This method provides a clearer and more declarative approach to building data structures with embedded discriminators.

    import { Schema } from "@&#8203;effect/schema";
    
    const User = Schema.TaggedStruct("User", {
      name: Schema.String,
      age: Schema.Number,
    });
    
    // `_tag` is optional
    const userInstance = User.make({ name: "John", age: 44 });
    
    assert.deepStrictEqual(userInstance, {
      _tag: "User",
      name: "John",
      age: 44,
    });

    Multiple Tags

    While a primary tag is often sufficient, TypeScript allows you to define multiple tags for more complex data structuring needs. Here's an example demonstrating the use of multiple tags within a single struct:

    import { Schema } from "@&#8203;effect/schema";
    
    const Product = Schema.TaggedStruct("Product", {
      category: Schema.tag("Electronics"),
      name: Schema.String,
      price: Schema.Number,
    });
    
    // `_tag` and `category` are optional
    const productInstance = Product.make({ name: "Smartphone", price: 999 });
    
    assert.deepStrictEqual(productInstance, {
      _tag: "Product",
      category: "Electronics",
      name: "Smartphone",
      price: 999,
    });

    This example showcases a product schema that not only categorizes each product under a general tag ("Product") but also specifies a category tag ("Electronics"), enhancing the clarity and specificity of the data model.

v0.67.13

Patch Changes

v0.67.12

Compare Source

Patch Changes

v0.67.11

Compare Source

Patch Changes

v0.67.10

Compare Source

Patch Changes

v0.67.9

Compare Source

Patch Changes

v0.67.8

Compare Source

Patch Changes
  • Updated dependencies [c1e991d]:
    • effect@3.2.1

v0.67.7

Compare Source

Patch Changes

v0.67.6

Compare Source

Patch Changes

v0.67.5

Compare Source

Patch Changes

v0.67.4

Compare Source

Patch Changes
  • #​2756 ee08593 Thanks @​gcanti! - Improving Predicate Usability of Schema.is

    Before this update, the Schema.is(mySchema) function couldn't be easily used as a predicate or refinement in common array methods like filter or find. This was because the function's signature was:

    (value: unknown, overrideOptions?: AST.ParseOptions) => value is A

    Meanwhile, the function expected by methods like filter has the following signature:

    (value: unknown, index: number) => value is A

    To make Schema.is compatible with these array methods, we've adjusted the function's signature to accept number as a possible value for the second parameter, in which case it is ignored:

    -(value: unknown, overrideOptions?: AST.ParseOptions) => value is A
    +(value: unknown, overrideOptions?: AST.ParseOptions | number) => value is A

    Here's a practical example comparing the behavior before and after the change:

    Before:

    import { Schema } from "@&#8203;effect/schema";
    
    declare const array: Array<string | number>;
    
    /*
    Throws an error:
    No overload matches this call.
    ...
    Types of parameters 'overrideOptions' and 'index' are incompatible.
    */
    const strings = array.filter(Schema.is(Schema.String));

    Now:

    import { Schema } from "@&#8203;effect/schema";
    
    declare const array: Array<string | number>;
    
    // const strings: string[]
    const strings = array.filter(Schema.is(Schema.String));

    Note that the result has been correctly narrowed to string[].

  • #​2746 da6d7d8 Thanks @​gcanti! - pick: do not return a ComposeTransformation if none of the picked keys are related to a property signature transformation, closes #​2743

v0.67.3

Compare Source

Patch Changes
  • Updated dependencies [6ac4847]:
    • effect@3.1.5

v0.67.2

Compare Source

Patch Changes
  • #​2738 89a3afb Thanks @​gcanti! - add cause in errors thrown by asserts, closes #​2729

  • #​2741 992c8e2 Thanks @​gcanti! - Schema.optional: the default option now allows setting a default value for both the decoding phase and the default constructor. Previously, it only set the decoding default. Closes #​2740.

    Example

    import { Schema } from "@&#8203;effect/schema";
    
    const Product = Schema.Struct({
      name: Schema.String,
      price: Schema.NumberFromString,
      quantity: Schema.optional(Schema.NumberFromString, { default: () => 1 }),
    });
    
    // Applying defaults in the decoding phase
    console.log(
      Schema.decodeUnknownSync(Product)({ name: "Laptop", price: "999" }),
    ); // { name: 'Laptop', price: 999, quantity: 1 }
    console.log(
      Schema.decodeUnknownSync(Product)({
        name: "Laptop",
        price: "999",
        quantity: "2",
      }),
    ); // { name: 'Laptop', price: 999, quantity: 2 }
    
    // Applying defaults in the constructor
    console.log(Product.make({ name: "Laptop", price: 999 })); // { name: 'Laptop', price: 999, quantity: 1 }
    console.log(Product.make({ name: "Laptop", price: 999, quantity: 2 })); // { name: 'Laptop', price: 999, quantity: 2 }

v0.67.1

Compare Source

Patch Changes
  • #​2890 5745886 Thanks @​gcanti! - Fix constructor type inference for classes with all optional fields, closes #​2888

    This fix addresses an issue where TypeScript incorrectly inferred the constructor parameter type as an empty object {} when all class fields were optional. Now, the constructor properly recognizes arguments as objects with optional fields (e.g., { abc?: number, xyz?: number }).

  • Updated dependencies [6801fca]:

    • effect@3.2.7

v0.67.0

Compare Source

Minor Changes
  • #​2634 d7e4997 Thanks @​gcanti! - ## Simplifying Type Extraction

    When we work with schemas, it's common to need to extract their types automatically.
    To make this easier, we've made some changes to the Schema interface.
    Now, you can easily access Type and Encoded directly from a schema without the need for Schema.Schema.Type and Schema.Schema.Encoded.

    import { Schema } from "@&#8203;effect/schema";
    
    const PersonSchema = Schema.Struct({
      name: Schema.String,
      age: Schema.NumberFromString,
    });
    
    // same as type PersonType = Schema.Schema.Type<typeof PersonSchema>
    type PersonType = typeof PersonSchema.Type;
    
    // same as Schema.Schema.Encoded<typeof PersonSchema>
    type PersonEncoded = typeof PersonSchema.Encoded;

v0.66.16

Compare Source

Patch Changes
  • Updated dependencies [1f6dc96]:
    • effect@3.1.3

v0.66.15

Compare Source

Patch Changes

v0.66.14

Compare Source

Patch Changes

v0.66.13

Compare Source

Patch Changes
  • Updated dependencies [e5e56d1]:
    • effect@3.1.1

v0.66.12

Compare Source

Patch Changes

v0.66.11

Compare Source

Patch Changes

v0.66.10

Compare Source

Patch Changes
  • Updated dependencies [18de56b]:
    • effect@3.0.7

v0.66.9

Compare Source

Patch Changes
  • #​2626 027418e Thanks @​fubhy! - Reintroduce custom NoInfer type

  • #​2631 8206529 Thanks @​gcanti! - add support for data-last subtype overloads in compose

    Before

    import { Schema as S } from "@&#8203;effect/schema";
    
    S.Union(S.Null, S.String).pipe(S.compose(S.NumberFromString)); // ts error
    S.NumberFromString.pipe(S.compose(S.Union(S.Null, S.Number))); // ts error

    Now

    import { Schema as S } from "@&#8203;effect/schema";
    
    // $ExpectType Schema<number, string | null, never>
    S.Union(S.Null, S.String).pipe(S.compose(S.NumberFromString)); // ok
    // $ExpectType Schema<number | null, string, never>
    S.NumberFromString.pipe(S.compose(S.Union(S.Null, S.Number))); // ok
  • Updated dependencies [ffe4f4e, 027418e, ac1898e, ffe4f4e]:

    • effect@3.0.6

v0.66.8

Compare Source

Patch Changes

v0.66.7

Compare Source

Patch Changes

v0.66.6

Compare Source

Patch Changes
  • #​2586 9dfc156 Thanks @​gcanti! - remove non-tree-shakable compiler dependencies from the Schema module:

    • remove dependency from Arbitrary compiler
    • remove dependency from Equivalence compiler
    • remove dependency from Pretty compiler
  • #​2583 80271bd Thanks @​suddenlyGiovanni! - - Fixed a typo in the JSDoc comment of the BooleanFromUnknown boolean constructors in Schema.ts

    • Fixed a typo in the JSDoc comment of the split string transformations combinator in Schema.ts
  • #​2585 e4ba97d Thanks @​gcanti! - JSONSchema: rearrange handling of surrogate annotations to occur after JSON schema annotations

v0.66.5

Compare Source

Patch Changes
  • #​2582 b3fe829 Thanks @​gcanti! - Add default title annotations to both sides of Struct transformations.

    This simple addition helps make error messages shorter and more understandable.

    Before

    import { Schema } from "@&#8203;effect/schema";
    
    const schema = Schema.Struct({
      a: Schema.optional(Schema.String, { exact: true, default: () => "" }),
      b: Schema.String,
      c: Schema.String,
      d: Schema.String,
      e: Schema.String,
      f: Schema.String,
    });
    
    Schema.decodeUnknownSync(schema)({ a: 1 });
    /*
    throws
    Error: ({ a?: string; b: string; c: string; d: string; e: string; f: string } <-> { a: string; b: string; c: string; d: string; e: string; f: string })
    └─ Encoded side transformation failure
       └─ { a?: string; b: string; c: string; d: string; e: string; f: string }
          └─ ["a"]
             └─ Expected a string, actual 1
    */

    Now

    import { Schema } from "@&#8203;effect/schema";
    
    const schema = Schema.Struct({
      a: Schema.optional(Schema.String, { exact: true, default: () => "" }),
      b: Schema.String,
      c: Schema.String,
      d: Schema.String,
      e: Schema.String,
      f: Schema.String,
    });
    
    Schema.decodeUnknownSync(schema)({ a: 1 });
    /*
    throws
    Error: (Struct (Encoded side) <-> Struct (Type side))
    └─ Encoded side transformation failure
       └─ Struct (Encoded side)
          └─ ["a"]
             └─ Expected a string, actual 1
    */
  • #​2581 a58b7de Thanks @​gcanti! - Fix formatting for Class and brands AST.

  • #​2579 d90e8c3 Thanks @​gcanti! - Schema: JSONSchema should support make(Class)

    Before

    import { JSONSchema, Schema } from "@&#8203;effect/schema";
    
    class A extends Schema.Class<A>("A")({
      a: Schema.String,
    }) {}
    
    console.log(JSONSchema.make(A)); // throws MissingAnnotation: cannot build a JSON Schema for a declaration without a JSON Schema annotation

    Now

    console.log(JSONSchema.make(A));
    /*
    Output:
    {
      '$schema': 'http://json-schema.org/draft-07/schema#',
      type: 'object',
      required: [ 'a' ],
      properties: { a: { type: 'string', description: 'a string', title: 'string' } },
      additionalProperties: false
    }
    */

v0.66.4

Compare Source

Patch Changes
  • #​2577 773b8e0 Thanks @​gcanti! - partial / required: add support for renaming property keys in property signature transformations

    Before

    import { Schema } from "@&#8203;effect/schema";
    
    const TestType = Schema.Struct({
      a: Schema.String,
      b: Schema.propertySignature(Schema.String).pipe(Schema.fromKey("c")),
    });
    
    const PartialTestType = Schema.partial(TestType);
    // throws Error: Partial: cannot handle transformations

    Now

    import { Schema } from "@&#8203;effect/schema";
    
    const TestType = Schema.Struct({
      a: Schema.String,
      b: Schema.propertySignature(Schema.String).pipe(Schema.fromKey("c")),
    });
    
    const PartialTestType = Schema.partial(TestType);
    
    console.log(Schema.decodeUnknownSync(PartialTestType)({ a: "a", c: "c" })); // { a: 'a', b: 'c' }
    console.log(Schema.decodeUnknownSync(PartialTestType)({ a: "a" })); // { a: 'a' }
    
    const RequiredTestType = Schema.required(PartialTestType);
    
    console.log(Schema.decodeUnknownSync(RequiredTestType)({ a: "a", c: "c" })); // { a: 'a', b: 'c' }
    console.log(Schema.decodeUnknownSync(RequiredTestType)({ a: "a" })); // { a: 'a', b: undefined }

v0.66.3

Compare Source

Patch Changes
  • Updated dependencies [a7b4b84]:
    • effect@3.0.3

v0.66.2

Compare Source

Patch Changes

v0.66.1

Compare Source

Patch Changes
  • Updated dependencies [1f6dc96]:
    • effect@3.1.3

[v0.66.0](https://togithub.com/Effect-TS/effect/blob/HEAD/packages/schema/CHANGELOG.md#06


Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner April 27, 2024 00:34
@renovate renovate bot requested review from Weakky and removed request for a team April 27, 2024 00:34
Copy link
Contributor

github-actions bot commented Apr 27, 2024

WASM Query Engine file Size

Engine This PR Base branch Diff
Postgres 2.043MiB 2.043MiB 0.000B
Postgres (gzip) 814.446KiB 814.453KiB -7.000B
Mysql 2.013MiB 2.013MiB 0.000B
Mysql (gzip) 801.126KiB 801.129KiB -3.000B
Sqlite 1.914MiB 1.914MiB 0.000B
Sqlite (gzip) 763.376KiB 763.382KiB -6.000B

Copy link

codspeed-hq bot commented Apr 27, 2024

CodSpeed Performance Report

Merging #4843 will not alter performance

Comparing renovate/driver-adapters-directory (b92a7e9) with main (9f3337c)

Summary

✅ 11 untouched benchmarks

@renovate renovate bot force-pushed the renovate/driver-adapters-directory branch 3 times, most recently from e4212fb to c2ec744 Compare May 4, 2024 10:17
@renovate renovate bot force-pushed the renovate/driver-adapters-directory branch 3 times, most recently from abeac44 to 643a2d0 Compare May 11, 2024 16:40
@renovate renovate bot force-pushed the renovate/driver-adapters-directory branch 6 times, most recently from f99c786 to 88278b1 Compare May 25, 2024 01:55
@renovate renovate bot force-pushed the renovate/driver-adapters-directory branch 3 times, most recently from 6ab5024 to ddf81f6 Compare June 1, 2024 04:31
@renovate renovate bot force-pushed the renovate/driver-adapters-directory branch 2 times, most recently from d609578 to 9a831ee Compare June 9, 2024 23:00
@renovate renovate bot force-pushed the renovate/driver-adapters-directory branch 7 times, most recently from a0d985e to 5833286 Compare June 16, 2024 22:35
@renovate renovate bot force-pushed the renovate/driver-adapters-directory branch from 5833286 to b92a7e9 Compare June 22, 2024 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants